Method and system for interfacing with a shipping service

ABSTRACT

A logistics node receives a purchase order from a customer. The logistics node selects an appropriate carrier to transport products specified in the purchase order and conveys shipping instructions to the selected carrier. The logistics node also coordinates the shipment by interacting with a source node (associated with a supplier of the products) and a destination node (associated with the recipient of the products). According to one exemplary feature, the logistics node provides an interface that permits users involved in the distribution chain to track the status of the shipments without having to enter tracking codes that are unique to individual carriers. According to another exemplary feature, the interface allows a user to access multiple “levels” of information regarding a shipment, including information pertaining to an individual product within a shipment containing multiple products. According to another exemplary feature, the interface allows a user to change the priority status associated with particular products that have already been presented for shipment. According to another exemplary feature, the interface provides different “views” for use by different respective users. Each of the views provides a corresponding different set of tools for use in interacting with the freight managing service.

[0001] This application claims the benefit of U.S. ProvisionalApplication No. 60/242,069, filed on Oct. 23, 2000, which isincorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention generally relates to a method and systemfor interfacing with a shipping service. More specifically, the presentinvention relates to a method and system for interfacing with a freightmanagement system that manages the transfer of products from a sourcesite to a destination site.

[0004] 2. Related Art

[0005] Some shipping carriers provide tracking tools that permitcustomers to track the status of shipments made by the carriers. Oneknown carrier, for instance, provides an Internet-accessible trackingtool that allows a customer to determine whether or not a packageshipped by the carrier has reached its intended destination. Inoperation, the customer queries the tool by inputting a unique packagenumber assigned by the carrier. The tool uses this number as an index toretrieve any status information that may have been entered regarding thepackage in the course of its delivery.

[0006] However, the above-described type of tracking tool haslimitations. Namely, a customer can extract information from this toolonly if the customer knows the identity of the carrier that is shippingthe package and the reference number (or numbers) assigned to thepackage by the carrier. Tracking packages based on the individual codesassigned by separate carriers may pose a burden on a customer who placesmultiple orders in the course of a day using several carriers. Further,a package-centric approach to product tracking (that is, where a packageidentification number is used to track the location of the product) maybecome ineffective if the products shipped in an initial package aretransferred to another package in the course of transit. That is, inthis case, a customer may not be able to examine the status of ashipment by inputting the reference number associated with the initialpackage.

[0007] Another drawback of known systems is that they generally provideonly rudimentary information regarding the location of a package.However, as appreciated by the present inventors, there may be manyaspects regarding the transfer of the products that may interestdifferent customers. For instance, a large package may contain severalitems. A customer cannot use the above-described Internet tool toinvestigate the contents of the package. Further, the package may becombined with other packages and shipped on a particular carrier. Acustomer cannot use the above-described Internet tool to broaden thesearch by examining the scope and composition of the overall shipment.

[0008] Another drawback of known systems is that they provide limitedprovisions for handling high priority shipments. For instance, if acustomer initially places a high priority on a shipment, the customerwill typically select a mode of transportation that ensures quick andreliable service (as opposed to slower, more unpredictable services).For instance, for a small package, the customer might opt to ship it byFederal Express, identifying that it is to be delivered to thedestination site the next business morning. A problem arises, however,when the user initially sends the product using a low priority service,and then later learns that the product should be delivered as a highpriority shipment (e.g., in a quicker time frame than was originallyanticipated). The known shipping services do not provide an effectivemechanism for allowing a customer to alter the priority of the shipmentonce the shipment is under way. Indeed, the known systems do not evenprovide a mechanism for identifying high priority products within, forinstance, a shipload of lower priority products. Hence, the highpriority products may be lost in a “sea” of lower priority items andcannot be targeted for expedited processing.

[0009] There is accordingly a need to provide a more effective interfacebetween a shipping service and its users.

SUMMARY OF THE INVENTION

[0010] The present invention addresses the above-identified needs, aswell as additional unspecified needs.

[0011] One exemplary aspect of the invention pertains to a logisticsnode for administering the shipment of a product from a source node to adestination node, including: an interface unit for coupling thelogistics node with at least one remote entity; a processing unitcoupled to the interface unit for controlling the operation of thelogistics node; a database coupled to the processing unit for storinginformation pertaining to the shipment of a product from the source nodeto the destination node; and tracking logic for receiving an inquiryfrom a user regarding a shipment being made by at least one of aplurality of possible carrier candidates, and in response thereto,providing information pertaining to the shipment. The inquiry does notrequire a user to specify carrier-specific information to successfullyretrieve information regarding the shipment.

[0012] Another exemplary aspect of the invention pertains to a logisticsnode for administering the shipment of a product from a source node to adestination node, including: an interface unit for coupling thelogistics node with at least one remote entity; a processing unitcoupled to the interface unit for controlling the operation of thelogistics node; a database coupled to the processing unit for storinginformation pertaining to the shipment of a product from the source nodeto the destination node; and interface administration logic forpermitting a first class of users to interact with the logistics nodeusing a first interface, the first interface providing access to a firstset of functions, and for permitting a second class of users to interactwith the logistics node using a second interface, the second interfaceproviding access to a second set of functions. The first set offunctions differs from the second set of functions, and wherein thefirst set of users are affiliated with the source node and the secondset of users are affiliated the destination node.

[0013] Another exemplary aspect of the invention pertains to a logisticsnode for administering the shipment of a product from a source node to adestination node, including: an interface unit for coupling thelogistics node with at least one remote entity; a processing unitcoupled to the interface unit for controlling the operation of thelogistics node; a database coupled to the processing unit for storinginformation pertaining to the shipment of a product from the source nodeto the destination node; logic for providing a user with an option toexamine shipment information using first and second levels of detail,wherein the second level of detail is more refined compared to the firstlevel of detail; logic for allowing a user to select the first or secondlevel of detail; and logic for providing shipping information to theuser corresponding to the selected level of detail.

[0014] Another exemplary aspect of the invention pertains to a logisticsnode for administering the shipment of a product from a source node to adestination node, including an interface unit for coupling the logisticsnode with at least one remote entity; a processing unit coupled to theinterface unit for controlling the operation of the logistics node; adatabase coupled to the processing unit for storing informationpertaining to the shipment of a product from the source node to thedestination node; and logic for permitting at least one user to change apriority level associated with at least one product.

[0015] Additional features and advantages of the invention areidentified in the ensuring discussion.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention can be understood more completely byreading the following Detailed Description of exemplary embodiments, inconjunction with the accompanying drawings, in which:

[0017]FIG. 1 shows an exemplary system for implementing the presentinvention;

[0018]FIG. 2 shows an exemplary work station for interacting with thesystem of FIG. 1;

[0019]FIG. 3 shows an exemplary logistics central station for use in alogistics node shown in FIG. 1;

[0020]FIG. 4 shows an overview of an exemplary process for performingaspects of the present invention;

[0021]FIG. 5 shows further exemplary detail pertaining to the process ofFIG. 4;

[0022]FIG. 6 shows an exemplary “Hot Parts List” process of the presentinvention;

[0023]FIG. 7 shows a message-exchange protocol pertaining to the processof FIG. 4;

[0024]FIG. 8 shows another message-exchange protocol pertaining to theprocess of FIG. 4, particularly pertaining the export of goods;

[0025] FIGS. 9A-9E show an exemplary series of screens appropriate to auser affiliated with the source node;

[0026] FIGS. 10A-10E show an exemplary series of screens appropriate toa user affiliated with the destination node;

[0027] FIGS. 11A-11C show an exemplary series of screens appropriate toa user affiliated with the customer node; and

[0028]FIGS. 12A and 12B show an exemplary series of screens appropriateto a user affiliated with the logistics node.

DETAILED DESCRIPTION OF THE INVENTION

[0029] 1. Exemplary System Architecture (FIGS. 1-3)

[0030]FIG. 1 shows an exemplary system 100 that may be used to implementthe principles disclosed herein. By way of overview, the system 100includes plural nodes. As used here, a node loosely represents an“actor” involved in the distribution of a product. A node may includephysical infrastructure, such as one or more physical facilities (e.g.,shipping centers, manufacturing plants, etc.), as well as informationtechnology (IT) equipment used at the facilities.

[0031] However, it should be noted that the equipment associated with aparticular node may be distributed over plural sites. Further, thesystem 100 may permit a user who is affiliated with a particular node touse any equipment to access functionality appropriate to the user'saffiliation, regardless of the location of the equipment. Accordingly, apiece of equipment owes its association with a node primarily based onthe affiliation of the user that gains access to the system 100 usingthe equipment. Accordingly, FIG. 1's depiction of the nodes (e.g., ashaving discrete “boundaries”) pertains more accurately to the logicalorganization of the system 100, rather than its literal physicalorganization.

[0032] The term “products,” as used herein, refers to any type oftransportable goods. For instance, the products may comprise parts usedto manufacture machines (such as automobiles), raw materials (such ascoal, scrap iron, etc.), chemicals and fuels (such as pesticides,fertilizers, gases under pressure, propane, etc.), consumer items (suchas electronic equipment, etc.), food (such as fruits, vegetables,processed and packaged foods, etc.), military cargo, and various othertypes of transportable goods. To facilitate explanation, portions of theensuing discussion are framed in the exemplary context of the supply ofparts to a manufacturing facility.

[0033] Turning now to the specifics of FIG. 1, a logistics node 108 actsas an information hub of the system 100. Namely, the logistics node 108receives communications from other nodes in the distribution chain, andbased thereon, coordinates the activities of the other nodes bytransmitting appropriate instructions to the other nodes.

[0034] The distribution chain itself includes three principal actors,including a source node 106, a customer node 104 and a destination node102. The customer node 104 generally represents an entity having abusiness objective which provides the impetus for the transfer ofproducts from a source site to a destination site. For instance, thecustomer node 104 may correspond to a department within a manufacturingenterprise having the responsibility to obtain products for amanufacturing plant. The source node 106 generally represents the entityresponsible for supplying the products at the command of the customernode 104. The destination node 102 generally represents the entity thatreceives the goods supplied by the source node 106. In a manufacturingcontext, for instance, the destination node 102 may represent a physicalplant used to manufacture a product using the products supplied thereto.

[0035] Other nodes in the system include one or more carrier nodes 110,one or more cross-dock nodes 112, one or more container return centernodes 114, one or more customs house broker nodes 116, and various othernodes 118 that may be appropriate to a particular business setting.Alternatively, a particular business setting may not require theservices of one or more of the nodes shown in FIG. 1.

[0036] The carrier nodes 110 represent various carriers that can beemployed to transport products from a source site to a destination site(or to some intermediary site). One or more carrier nodes 110 may beaffiliated with (and operated by) the logistics node 108. Other carriernodes may comprise separate business entities (e.g., separate commercialshipping carriers) that operate in an independent fashion from thelogistics node. In this case, the logistics node 108 presents a central“nerve center” which governs the activities of the carrier nodes 110,e.g., on a contractual basis.

[0037] Potential carriers include trucks, railway carriers, aircarriers, water-borne vessels, small package services, etc. Some ofthese services may operate by transporting products on fully loadedtransportation mechanisms (such as a fully loaded truck). Other of thesecarriers may allow for the transportation of products on less than fullyloaded transportation mechanisms (such as on trucks that are not at fullloading capacity) (referred to as Less Than full Loads, or LTLs). Eachof the carriers may operate one or more facilities for performing itsascribed shipping functions. Further, each of the carriers mayadminister a tracking service which allows it to monitor the location orstatus of products that it is carrying.

[0038] The cross dock nodes 112 may represent one or more facilitiesused to transfer products from one form of transportation to another.For instance, an exemplary cross dock node 112 may operate bytransferring products from one carrier to another carrier.Alternatively, another exemplary cross dock node 112 may operate bytransferring products from one type of package (e.g., container) toanother, but otherwise using the same carrier service to transport theproducts.

[0039] Different business settings may employ the services of differenttypes of cross dock nodes 112. In one setting, a cross dock node mayperform a consolidation function. That is, this cross dock node takesproducts received from multiple different sources and transfers theproducts to a single form of transportation (such as space allocated onan ocean-going vessel). In another business setting, the cross dock nodemay perform a deconsolidation function. That is, this cross dock nodesmay distribute products transported on a single mode of transportationto plural different forms of transportation. In still other businesssettings, the cross dock node may perform a freight forwarding function.In this context, the node simply receives and reships the products(e.g., using a different form transportation).

[0040] The container return center node(s) 114 may represent one or morefacilities used to store and/or manage a collection of containers usedin transporting the products.

[0041] The customs house broker node(s) 16 may represent one or morefacilities used to interact with one or more governments 190 for thepurpose of obtaining clearance to either import goods from anotherjurisdiction (e.g., country) or to export goods to another jurisdiction(e.g., country). Obviously, shipping activities that take place within asingle country can dispense with the services of these nodes.

[0042] Finally, other nodes 118 may be included to accommodate theunique requirements of particular business environments.

[0043]FIG. 1 indicates that multiple links can be used to interconnectthe plural nodes of the system. One exemplary link 180 used to connectthe nodes is the Internet. An Internet link may be desirable so as totake advantage of the global accessibility and wide acceptance of thisform of communication. Another exemplary link 182 used to connect thenodes is the Electronic Data Interchange (EDI) (which pertains to awell-known protocol used to exchange business documents in a structuredand pre-defined format). An EDI link may be desirable so as toaccommodate users that already have an EDI processing infrastructure inplace, and who accordingly prefer to continue transacting business usingthis protocol. In any given transaction, communication may be conductedentirely using the Internet, entirely using the EDI protocol, or byusing the Internet to exchange some messages and the EDI service toexchange other messages.

[0044] More generally, the particular business environment may influencethe propriety of the links used to interconnect the various nodes.Alternative types of links that can be used include: an intranetnetwork; a PAN (Personal Area Network); a LAN (Local Area Network); aWAN (Wide Area Network) or a MAN (Metropolitan Area Network); a storagearea network (SAN); a frame relay connection; an Advanced IntelligentNetwork (AIN) connection; a synchronous optical network (SONET)connection; a digital T1, T3, E1 or E3 line connection; a Digital DataService (DDS) connection; a DSL (Digital Subscriber Line) connection; anEthernet connection; an ISDN (Integrated Services Digital Network) lineconnection; a dial-up port such as a V.90, V.34 or V.34bis analog modemconnection; a cable modem connection; an ATM (Asynchronous TransferMode) connection; an FDDI (Fiber Distributed Data Interface) connection;etc. The communication links may furthermore comprise (or provide accessto) various types of wireless communication systems, including: a WAP(Wireless Application Protocol) link; a GPRS (General Packet RadioService) link; a GSM (Global System for Mobile Communication) link; aCDMA (Code Division Multiple Access); a TDMA (Time Division MultipleAccess) link; etc.

[0045] The links may further operate using a variety of known networkenabling code, such as Hyper text Markup Language (HTML), Dynamic HTML,Extensible Markup Language (XML), Extensible Stylesheet Language (XSL),Document Style Semantics and Specification Language (DSSSL), CascadingStyle Sheets (CSS), Synchronized Multimedia Integration Language (SMIL),Wireless Markup Language (WML), Java™, Jini™, C, C++, Perl, UNIX Shell,Visual Basic or Visual Basic Script, Virtual Reality Markup Language(VRML), and a variety of other types of protocols and/or platforms. Theprotocol deemed appropriate for use may depend, in part, on thetechnology currently being used by the parties involved in the shippingtransaction, as well as the requirements of a particular application.

[0046] The information technology (IT) infrastructure employed by eachof the nodes may vary widely depending on the equipment already in placeat these nodes. With exemplary reference to the destination node 102, atypical organizational setting may provide one or more work stations(e.g., work stations 150 and 154) communicatively coupled to a centralstation 152. The destination node 102 may use an intranet or other typeof local network to interconnect the work stations (150, 154) and thecentral station 152. The work stations (150, 154) may directly accessthe other sites in the system 100. Alternatively, the work stations(150, 154) may access other sites in the network 100 via the centralstation 152.

[0047] Firewall 156 provides conventional functionality for protectingthe resources of the node from the deleterious impact of eventsoccurring external to the node. The firewall 156 may also serve toprevent users within the node from taking actions that might jeopardizethe integrity of node resources. In connection therewith, the node mayuse various encryption algorithms (such as SSL 128 bit encryption) whenexchanging information with external resources and networks. Yet othersecurity provisions may be used by the node, as will be apparent tothose skilled in the art.

[0048]FIG. 1 shows that other nodes in the system 100 may have similarinformation technology infrastructures to destination node 102. Namely,customer node 104 includes work stations 160 and 164 tied to customercentral station 162. Source node 106 includes work stations 170 and 174tied to a central station 172. Logistics node 108 includes work stations140 and 142 tied to a central station 144. Nodes 104, 106 and 108 mayalso employ associated firewall functionality 166, 176 and 146,respectively.

[0049] Although not shown, the other nodes in the system 100 (e.g.,nodes 110, 112, 114, 116 and 118) may also each include a number ofworkstations and/or a central station, as well as additional equipmentappropriate to these nodes.

[0050] In addition, the system 100 may include a number of separate workstations (e.g., work stations 196 and 197) that maintain remoteaffiliation with one or more nodes. More specifically, a work station'saffiliation may depend on the affiliation of the user operating the workstation. As such, a user associated with the customer node 104, forinstance, can use any remote work station (such as work stations 196 or197) to access functionality appropriate to the customer node. Thesystem 100 may grant or block access to particular functionality basedon the user's password (or other identifying information input to thework station).

[0051]FIG. 2 shows an exemplary work station (e.g., work station 154)for interacting with system 100 of FIG. 1. The work station includes anytype of general or special purpose computer comprising conventionalhardware, such as a bus 214 connected to a RAM memory (Random AccessMemory) 206, ROM memory (Read-Only Memory) 204, storage device 202,processor 216, and communication interface 218 (which provides access toremote resources via communication line 220). The processor 216 cancomprise any type of microprocessor or other logic-executing unit, suchas an Intel x86-based device, etc. The processor 216 may further executeinstructions specified by any type of operating system program, such asMicrosoft Windows™, etc. The storage device 202 may comprise any type ofstorage media, such as any type of magnetic or optical media (e.g.,CDROM).

[0052] The work station 154 further includes an input/output interfaceunit 208. The interface unit 208 may include one or more renderingdevices 210 for presenting information to a user (e.g., using a display,printer, audio output, etc.). The interface unit 208 may further includeone or more input devices 212 for use in inputting information to thework station 154 (e.g., using a keyboard, touch-sensitive panel orscreen, speech recognition input, etc.).

[0053]FIG. 2 indicates that the work station 154 also includes additionfunctionality 222. This additional functionality 222 may representdifferent programs and/or hardware for implementing one or morefunctional features provided by the work station 154. For instance, thework station 154 may include security logic 224 for performing varioussecurity-related functions, and reporting/analysis logic 226 forperforming various reporting and/or analysis functions based oninformation obtained from the logistics node 108. The work station 154may incorporate yet further functionality (not shown) appropriate toparticular business settings.

[0054] In an alternative embodiment, various other types of workstations can be used to interact with the system 100. For example, thework station can be embodied as any type of wireless mobile station(e.g., having Internet browsing capability), a radio-enabled Palm™ Pilotor similar unit, various types of “smart” appliances, various modulesinstalled in one or more vehicles, etc. The work station mayadditionally include means for receiving Global Positioning System (GPS)data. Such data may allow the work station to determine its position andto forward its position to the logistics node 108. Such data, forinstance, may better enable the logistics node 108 to determine thestatus of a delivery (e.g., by tracking the location of a carrier).

[0055]FIG. 3 shows an exemplary structure of the central station 144used in the logistics node 108. The central station 144 includes atleast one processing logic unit 306 (e.g., CPU) connected to at leastone memory device 302, at least one database 308, and at least onecommunication interface 304. The interface 304 allows the centralstation 144 to interact with various external entities, such as othernodes in the system 100. The central station 144 may embody varioustypes of architectures, such as a mainframe architecture, a serverarchitecture (e.g., in the context of a client-server environment), orsome hybrid form of architecture. In one embodiment, for instance, thecentral station 144 uses mainframe technology to ensure the reliabilityand integrity of its services, but includes a “front end” that allows itto interact with the Internet (or other network). Still otherarchitectures are possible to accommodate the existing equipment used byvarious business entities, and to take account for various otherconsiderations.

[0056] The database 308 contains various information concerning theshipment of products, as discussed in further detail in section No. 3below. The database 308 can be implemented using any type of storagemedia. For instance, it can comprise a hard-drive, RAM memory, magneticmedia (e.g., discs, tape), optical media, etc. Further, the database maybe implemented as a an Oracle™ relational database sold commercially byOracle Corp. Other database protocols can be used to implement thedatabase, such as Informix™, DB2 (Database 2), Sybase, etc. The database308 may comprise a single archive of information maintained at a singlesite, or may comprise a group of interconnected archives retaininginformation in a distributed fashion. Further, parts of the database 308may be located at facilities that are remote from the central station144.

[0057] According to a variation, various modules of the logisticscentral station 144 can be implemented as separate computers. Theseparate computers (not shown) may be located together in one facilityor located remotely from each other.

[0058] The logistics central station 144 may also include a number ofprograms 310. The programs 310 may include security logic 312 forensuring the integrity of various functionality and resources providedby the logistics central station 144. The security logic 312 may furtherinclude an encryption/decryption engine (not shown) for encrypting anddecrypting information transmitting from/to the central station 144.

[0059] The programs 310 may also include database management logic 314used for storing, retrieving and/or otherwise manipulating informationstored in the database 308.

[0060] In addition, the programs 310 may include interfaceadministration logic 316 for providing a number of different interfacesthat can be used by work stations to interact with the central station144. For instance, the logistics central station 144 may provide a firstinterface for users associated with the source node 106, a secondinterface for users associated with the destination node 102, and athird interface for users associated with the customer node 104. Asexplained in further detail in section No. 3 below, these threeinterfaces provide access to respective different sets of toolsdepending on the node with which the user is affiliated (e.g., asreflected by the user's password entered into the work station).

[0061] The programs 310 may also include freight management logic 318.This logic performs various tasks involved in the shipment of productsfrom a source site to a destination site, such as calculation ofshipping plans, the determination of preferred carriers, etc.

[0062] Additional logic (not specifically identified in FIG. 3) can beincluded to implement each of the functions identified in section Nos. 3and 4 of this application. For instance, the logistics central station144 can include separate programs/logic to implement each of thefunctions accessible via the interface screens discussed in section No.3 below.

[0063] The central stations used in other nodes may resemble thearchitecture shown in FIG. 3 (but will include functionality appropriateto the services and operations provided by the other respective nodes).

[0064] 2. Exemplary System Operation (FIGS. 4-8)

[0065] 2(a). Exemplary Freight Processing Overview (FIG. 4)

[0066]FIG. 4 provides a high-level overview of an exemplary process forshipping products using the system of FIG. 1. It begins in step 402,where the customer node 104 transmits purchase orders to the logisticsnode 108. These purchase orders contain instructions that direct thesource node 106 to deliver products to the destination node 102. (Asdescribed above, the customer node 104 may represent a corporate entitythat generates the purchase orders to direct a supplier to ship productsto one of the corporation's manufacturing plants.)

[0067] The logistics node 108 then forwards the orders to the sourcenode 106 in step 404. In step 406, the source node 106 receives,reviews, and confirms the orders. More specifically, the source node 106may confirm the orders with or without making changes to the orders.Notice of the source node's confirmation (and any alterations in theorders) is then sent back to the logistics node 108.

[0068] A carrier then picks up the goods at the source node 106, whichprompts the source node 106 to generate a shipping notice (in step 408).

[0069] Thereafter, in step 410, the carrier delivers the goods to thedestination node 102, which prompts the destination node 102 to notifythe logistics node 108 of this event (in step 412).

[0070] 2(b). Exemplary Detailed Process Flow (FIG. 5)

[0071]FIG. 5 illustrates an elaboration on the principal steps shown inFIG. 4 in one exemplary shipping context. As to presentation scheme,FIG. 5 groups the steps into categories demarcated by dashed horizontallines to indicate the “actors” responsible for performing the steps. Theactors include a logistics node, customer node, source node, anddestination node (such as, respectively, the logistics node 108,customer node 104, source node 106, and destination node 102 shown inFIG. 1). Further, FIG. 5 groups the steps into categories demarcated bydashed vertical lines to indicate shipping phases in the process flow.The phases include a “prior to ship date” phase 502, a “ship date” phase504, and an “arrival date” phase 506. As these labels suggest, the“prior to ship date” phase 502 corresponds to those actions performed bythe system prior to the date that the products are shipped from thesource site. The “ship date” phase 504 corresponds to those actionsperformed substantially on the date that the products are shipped fromthe source site. The “arrival date” phase 506 corresponds to thoseactions performed substantially on the date the products arrive at thedestination site.

[0072] The process starts out in step 518. In this step, the customersends a weekly release batch file to the logistics node. In oneexemplary embodiment, the release batch file identifies the customer'spurchase orders over a time span of one or more weeks (e.g., in oneexemplary embodiment 15 to 17 weeks in the future). Each purchase ordermay specify one or more products, one or more suppliers that willfurnish the products, and one or more destination sites that willreceive the products. (Note that step 518 generally corresponds to step402 in FIG. 4.)

[0073] The customer can use any technique to transfer the batch file tothe logistics node. The technique used may depend on communicationequipment in place at the customer node and/or the logistics node. Forexample, the customer may transfer the batch file using e-mailmessaging. Upon receipt, the logistics node may then manually transferthe information contained in the e-mail message to an appropriate file(or files) in the logistics node. In an alternative embodiment, thecustomer may use any type of electronic transfer which directly feedsthe batch file into the appropriate receiving file(s) maintained by thelogistics node, thus eliminating the need for any type of manualtransfer operations.

[0074] The logistics node receives the file and, in step 520, processesthe current and next week's purchase orders. Part of this processing mayinvolve comparing the purchase orders identified in the most recentbatch file with purchase orders identified in a previous batch file foran identified time period, such as the current week. The most recentbatch file may differ from a previous batch file because a customer mayhave canceled a previous order, added a new order, or changed any of theattributes of a pending order (such as product numbers, quantities,suppliers, destinations, etc.). These discrepancies are resolved in anappropriate manner, e.g., by updating the purchase order filesmaintained by the logistics node.

[0075] Another part of the processing encompassed by step 520 may entailreviewing a prior week's orders vis-a-vis the orders that were actuallyexecuted to identify discrepancies. For instance, the comparison mayindicate that some orders were not executed. The logistics node notesthese discrepancies and addresses these discrepancies in an appropriatemanner, e.g., by canceling or rescheduling the orders.

[0076] In step 522, the logistics node sends the release file (i.e.,purchase order file) to an “engineering” department for analysis. Thisdepartment may perform various network planning studies on the basis oforders placed in a defined time span (such as several weeks).

[0077] Then, in step 524, the logistics node runs a release fileprocessing error log report. This processing may involve examining theorders to identify any undefined information. For instance, the releasefile may contain product codes, supplier identifiers, destination siteidentifiers, etc., that the logistics node has not previouslyencountered, and may therefore have difficulty interpreting. Thelogistics node culls out this undefined information and places it in aseparate holding file (for later separate processing).

[0078] Step 526 involves maintaining a master database that storesshipping information. This information may pertain to the physicalcharacteristics of the products (e.g., size and weight of the products),the physical characteristics of the packages (e.g., boxes) used to housethe products, and/or the physical characteristics of the containers(e.g., racks, palettes, etc.) used to transport the packages on thecarriers. The information may also pertain to the physicalcharacteristics and constraints of the shipping space provided byvarious carriers. The information may also pertain to the rates chargedby various carriers.

[0079] In step 528, the logistics node plans orders into “shippablequantities.” One aspect of this step involves scheduling the shipmentsso as to even out flow of products arriving at the destination sites.This ensures that the destination sites are not deluged with a largenumber of deliveries on one day of the week. The logistics node may makethis determination based, in part, on prior analysis performed in step522.

[0080] Another aspect of step 528 involves scheduling the shipments froma supplier (i.e., source site) so as to consolidate shipments. Forinstance, the customer may request that a particular supplier make twoseparate shipments on two respective days in one week. In this case, thelogistics node may combine these shipments into a single shipment (ifpossible) to reduce shipping costs.

[0081] Another aspect of step 528 involves selecting a suitable mode oftransportation to ship the products. For instance, in one particularembodiment, the logistics node selects one of three different shipmentmodes to transport the products. The modes comprise: (1) a small packageshipment; (2) a “Less Than Truckload (LTL) shipment (pertaining to ashipment that does not fill an entire truckload); and (3) a fulltruckload shipment. In determining the mode, the logistics node 108 maydraw from the information maintained in step 526 (discussed above).

[0082] The logistics node then contacts the supplier in step 530 toconvey a proposed (e.g., tentative) shipment plan to the supplier. Aswill be described in greater detail in section No. 3 below, the supplierreviews the tentative plan to determine whether it can satisfy theorder. For instance, the supplier determines whether it can ship therequested quantity of goods on the requested shipment date. If so, thesupplier confirms the plan without revisions. If the supplier cannotsatisfy the requested shipment, the supplier may revise the plan andthen communicate its revision back to the logistics node. The logisticsnode uses the revised plan to generate a modified shipping plan (ifpossible). (The above described series of operations generallycorresponds to steps 404 and 406 of FIG. 4.) If the source node has madechanges to the orders, the logistics node runs a report showing thesechanges (in step 536).

[0083] The logistics node then advances to step 534 to perform replanshipment processing. This step may allow the logistics node to reviewproblematic shipments and make any changes that may be appropriate. Forinstance, the source node may have identified potential problems in theshipment plan. For example, the logistics nodes may have initiallyspecified that the shipment was to use an LTL carrier. The supplier,however, may have objected to this mode of shipment in step 530 (e.g.,by forwarding comments to the logistics node through an appropriatelyconfigured confirmation screen). Alternatively, the impracticality (orinefficiency) of a plan may have been recognized through independentmeans. In any event, the replan step gives the logistics node anopportunity to revisit the plan and make any changes that may beappropriate. One or more interface screens may be provided to facilitatethis task (as will be discussed in section No. 3 of this application).For instance, one exemplary replanning screen gives the user a chance tobreak the shipment up into multiple parts to resolve schedulingdifficulties.

[0084] In one embodiment, the above-described replanning operation maybe executed by logistics personnel. In another embodiment, thereplanning operation may be performed by source site personnel (e.g., bya supplier). In another embodiment, the replanning responsibility may beshared between the logistics node and the source node.

[0085] In step 532, the logistics node runs a supplier shipment schedulereport.

[0086] In steps 534-538, the logistics node analyzes the orders andselects one or more carriers to transport the products. Various criteriacan be used to govern the selection of carriers. For instance, thelogistics node can maintain a list of preferred carriers. The logisticsnode may select carriers from this list based on their availability andability to perform the shipment, and also based on their respectiverates. That is, in one exemplary embodiment, if multiple carriers areavailable to make a shipment, the logistics node may select the leastexpensive carrier. Steps 534-536 may also determine whether it is mostefficient to schedule the shipment in a series of separate “legs.” Forinstance, the logistics node may determine whether it is desirable touse a LTL carrier to pick up the product at the source node, andthereafter combine the product with other shipments at one or more crossdock nodes.

[0087] In step 538, the logistics node conveys instructions to one ormore carriers (e.g., the “tender carrier” subtask of step 538). In step540, the carrier(s) receive and acknowledge their respective shippinginstructions. In step 542, the logistics node runs various load reports(appropriate to a particular shipping context). In step 544, thelogistics node updates the movements of the carrier.

[0088] In step 550, the carrier arrives at the source node. In step 548,the carrier then sends its movement pickup status to the FMfunctionality of the logistics node. This information is received by thelogistics node in step 546, upon which the logistic node updatesshipment status information.

[0089] The supplier updates its shipping notice information in step 552to reflect the loading of the carrier (in step 538). The supplier thenforwards shipping status information to the logistics node. In step 554,the logistics node responds to this information by running a reportshowing the confirmed shipping plans vs. actual shipping plans (in step554). This step identifies differences between the planned shipment andthe shipment that was actually loaded on the carrier. In step 556, thelogistics node updates its internal database to reflect the items thatactually were shipped.

[0090] After being loaded (in step 558), the carrier moves the freightin step 560, and eventually arrives at the destination node in step 564.(Note that this step generally corresponds to step 410 in FIG. 4). Thedestination node responds by capturing arrival event detail (such astrailer ID) (in step 568). In step 570, the destination node may examinedetailed information pertaining to the contents of the trailer that hasarrived. This capability is further discussed in section No. 3 of thisapplication. By way of preview, the destination node may determinewhether there are any priority items on a particular shipment byexamining a screen which breaks down a load to its individual productconstituents. The shipment assumes the priority level of the product inthe shipment having the highest priority level.

[0091] The carrier also sends its movement delivery status to the FMfunctionality of the logistics node in step 572. (This step generallycorresponds to step 412 in FIG. 4). In step 575, the logistics noderesponds by updating the status of the carrier.

[0092] 2c. Hot List Processing (FIG. 6)

[0093]FIG. 6 shows a process for changing the priority status ofshipments. In step 618, the logistics node receives a list of “hot”items. Such items are deemed “hot” because they require expeditedhandling or delivery.

[0094] In step 620, the logistics nodes compares the list of “hot” itemsagainst a master list of items. The master list identifies products thatthe system is currently obligated to ship on behalf of its customers.The system may cull out those items in the list of “hot” items that arenot present in the master list.

[0095] In step 624, the logistics node may receive updates regardingpriority items from a plurality of modes of communication, such astelephone, facsimile, e-mail, etc.

[0096] In steps 622 and 626, the logistics node processes the collectedpriority information to resolve the priority status of products, and togenerate one or more reports appropriate to a particular shippingenvironment.

[0097] In step 628, the logistics report updates confirmed releases(purchase orders) and shipments in the FM functionality. In this step,the logistics node may further change the priority level assigned to theproducts. Section No. 3 of this application provides further details onexemplary mechanisms for performing this task.

[0098] In step 630, the logistics node terminates the priorityprocessing routine by updating the movements of the products using theFM functionality.

[0099] 2(d). Exemplary Message-Exchange Protocol (FIG. 7)

[0100]FIG. 7 identifies messages exchanged between nodes in the systemof FIG. 1 when performing the general processes discussed in connectionwith FIGS. 4 and 5.

[0101] The process begins when the customer node 104 sends a copy ofPurchase Orders (PO), Materials Requisition (MR) or Supplier DailySchedules (SDS) to the logistics node 108 (note transfer path 708 inFIG. 7, labeled “PO/MR/SDS”). (Note that his operation generallycorresponds to step 402 in FIG. 4 and step 518 in FIG. 5). In oneexemplary embodiment, the customer may transmit this information to thelogistics node 108 two to three days in advance of shipping. Thelogistics node 108 receives and stores a copy of this information. Thecustomer may also directly transmit this information to the source node106.

[0102] The logistics node 108 combines the received PO/MR/SDS messagewith shipping instructions to form supplemented information. Thelogistics node 108 sends this supplemented information to the sourcenode 106 (note data path 718). The transmitted information may includean identification of: (a) the products and quantities to be shipped; (b)the date and time when the products are required; (c) the destinationthat the products should be shipped to; and (d) the carrier that will bepicking up the products. (Note that this step generally corresponds tostep 404 of FIG. 4).

[0103] Upon receipt of the above information, the supplier (at sourcenode 106) confirms its ability to supply the products on the requestedterms or on modified terms. (This step generally corresponds to step 406of FIG. 4 and step 530 of FIG. 5). The supplier's confirmation mayidentify the quantity of products that the supplier 106 has availablefor shipment and the date and time that the supplier can make theshipment. In response to this message, the logistics node 108 notes anyvariation between its original order requirements and the modifiedorders specified by the supplier.

[0104] After performing various shipment planning functions (describedabove with reference to FIG. 5), the logistics node 108 tenders a loadto the carrier 110 (in path 734). Thereafter, the carrier node 110 maysend shipment status information at milestones in the load's transit (inpath 736).

[0105] When the carrier leaves the source node 106 with a given order,the supplier sends a message to the logistics node 108 informing thesource node 106 of the makeup of the actual shipment loaded onto thecarrier (note path 720). (Note that this step generally corresponds tostep 408 in FIG. 4, and step 552 in FIG. 5). A bill of lading is alsoprinted at this time. The shipping notice information (i.e., the AdvanceShipping Notice or “ASN”) may contain the following information: (a) theactual quantity of products shipped; (b) the actual date/time shipped;(c) the carrier and trailer number of the shipping carrier; and (d) abill of lading number.

[0106] The logistics node 108 then sends the customer node 104 astandard ASN transaction assembled from the information collected fromthe source node 106 (in path 712). Alternatively, the source node 106may send ASN information directly to the customer node 106. In thiscase, the customer node 104 sends the ASN information to the logisticsnode 108 (in path 710).

[0107] The logistics node 108 also forwards a load plan for outboundshipments to the cross dock node 112 (in path 724). The logistics node108 may generate the load plan using an optimization process, such asconsolidation analysis, breakdown analysis, cross dock/pooling pointanalysis, carrier selection analysis, etc. In response, the cross docknode 112 loads the outbound trailers as inbound trucks arrive.

[0108] The logistics node 108 also sends the cross dock node 112 ASNinformation received from the suppliers (in path 725). The cross dockuses this information to plan daily work assignments. Thereafter, thecross dock node 112 notifies the logistics node 108 when a trailer hasarrived (in path 726). This information is used by logistics node 108 intracking the progress of the products through the chain of distribution.Such tracking information can also be forwarded to the customer node104. Among other uses, this information provides an indication of howquickly a facility can “cross dock” a given product. Finally, the crossdock node 112 notifies the logistics node 108 when a trailer hasdeparted from its facilities (in path 728). This information enables thelogistics node 108 to track the progress of the shipment and also allowsthe destination node 102 to plan for receipt of the products. Further,this information allows the logistics node 108 to determine how quicklythe cross dock node 112 is processing shipments through its facilities(that is, when this information is combined with previously transmittedinformation regarding the receipt of the shipment at the cross dock node112).

[0109] The destination node 102 notifies the logistics node 108 uponarrival of the trailer (in path 704). This information is used for: (a)yard management logging of arrived but not unloaded trailers; (b)carrier performance reporting; and (c) timely completion of activitiesin the system. (Note that these operations generally correspond to steps410 and 412 or FIG. 4, and step 572 of FIG. 5).

[0110] The destination node 102 then notifies the logistics node 108when the trailer has been unloaded and the products received into theirinventory (in path 702). This information is used for: (a) yardmanagement logging of empty trailers; (b) performance reporting for thecustomer receiving location; and (c) notification to suppliers thatpayment will soon be processed.

[0111] Reusable container inventories used by the suppliers at thesource node 106 should be replenished regularly to maximize utilizationof containers. In connection therewith, the supplier may send a messageto the logistics node 108 (in path 716) requesting a replenishment ofthe supplier's container inventory. The logistics node 108 thenschedules container return shipments from the container return node 114to the source node 106. The logistics node 108 then sends a request forcontainer shipments to the container return node 114 (in path 731).Information transferred in this communication may include an indicationof: (a) the container type(s) that are being requested; (b) thequantities to be shipped; (c) the date and time when the containers areneeded; (d) where the product will be shipped; and (e) the carrier thatwill pick up the containers. The container return node 114 then confirmsthe request for containers by transmitting a message back to thelogistics node 108 that specifies a quantity available to be shipped anddate and time on which they can be shipped. The logistics node 106 notesany divergence between the amount of containers requested and the amountoffered.

[0112] Further, the container return node 114 may independently notifythe logistics node 108 when it is ready to provide containers (in path730). The logistics node 108 uses this information to schedule a timewhen these containers can be picked up and returned to the source node106. Further, containers on inbound shipments to the destination node102 may be sent to the container return node 114 so that a givensupplier can decrement its inventory of containers (in path 732).

[0113] Further, the logistics node 108 may request product/packaginginformation from the source node 106 (in path 714). The logistics node108 updates its database when it receives this information. Weight andcube information contained in this information is particularly useful inbuilding shipments (e.g., as described with exemplary reference to step528 of FIG. 5).

[0114] Further, the destination node 102 notifies the logistics node 108when it is projected to “run out” of products necessary to perform itsfunction (in path 706). Such information may be valuable for trackingpurposes, and to anticipate and appropriately react to shortages inproducts.

[0115] The logistics node 108 may store information pertaining toshipments in its database 308 (such as, but not limited to, the shippinginformation discussed above). The logistics node may further allow usersto access the stored information (if the user's are deemed to haveappropriate authorization to view the information). In this sense, theinformation maintained by the logistics node 108 is “visible” to usersassociated with different nodes. FIG. 7 illustrates this aspect of thesystem using the double-headed arrow bearing the legend “full visibilityto inbound freight.”

[0116] The above-discussed messaging between nodes can be performedusing, for instance, the Internet, EDI, or some combination of these twoprotocols, or some other type of protocol.

[0117] 2(e). Exemplary Freight Processing for an Export Application(FIG. 8)

[0118] The message-exchange protocol shown in FIG. 7 is particularlyapplicable to the transfer of goods from a supplier to a manufacturingplant within the borders of a single jurisdiction (e.g., a singlecountry). Nevertheless, the basic protocol identified in that figure canbe applied to various other situations involving the transfer ofproducts from a source site to a receiving site. For instance, theprotocol described in FIG. 7 can be applied to the export or import ofgoods across jurisdictional boundaries (such as from one country toanother).

[0119]FIG. 8, for example, pertains to a modification of the techniqueof FIG. 7 for exporting products using an air carrier. At least twoaspects of the process of FIG. 8 differ from the protocol of FIG. 7.First, the international aspects of the shipment require the involvementof customs house broker (CHB) nodes 118. Second, the internationalaspects of the shipment typically involve more complex carrier and crossdocking interaction. These two aspects are emphasized below in thediscussion of FIG. 8. Other aspects of the exchange have been previouslyexplained with reference to the protocol of FIG. 7, and accordingly arenot repeated below.

[0120] As to the customs house broker (CHB) aspects of FIG. 8, thelogistics node 108 typically forwards a copy of documentation necessaryfor customs clearance to the CHB node 116 (in path 838 of FIG. 8). Thisdocumentation may include information such as bills of lading, invoices,shipment contents, etc. The CHB node 116, in turn, may forward exportcompliance and other related documentation to an appropriate governmentagency (in path 840). When the government agency notifies the CHB node116 of the export's clearance, the CHB sends a status report to thelogistics node 108 (in path 842) to notify that node of the clearance.The CHB's status report may alternatively include an update about anyshipments delayed or detained at customs. The logistics node 108receives the status information and stores this information in form thatmay be accessed by authorized parties, thus further enhancing the“visibility” of the interface.

[0121] In an import context (not shown), the CHB node 116 notifies thelogistics node 108 when a shipment clears customs using a deliveryorder. This triggers the logistics node 108 to arrange the next stage ofthe product's transportation.

[0122] As to the carrier and cross docking aspects of FIG. 8, thein-land carrier sends a request for air containers to load the product(path 832). The logistics node 108 then passes the request on to the aircarrier node (in path 828). It may further be necessary to reserve spaceon a given air craft or vessel by specifying a shipment date on aselected air craft or vessel (in path 826). Both the in-land carriernode 110 and the air carrier node 110 may regularly send shipment statusand tracking information to the logistics node 108 (e.g., in paths 834and 830, respectively).

[0123] The freight forwarder node 112 functions in a similar manner tothe cross-dock node 112 in FIG. 5. In addition, export or import usingan ocean-going vessel may require processing at aconsolidating/deconsolidating node (not shown in FIG. 8).

[0124] 3. Exemplary Interface Features (FIGS. 9-12)

[0125] 3(a). Overview of Screen Presentations

[0126] As mentioned above, the logistics node 108 provides plural levelsof access to the shipping service corresponding to plural respectiveclasses of users. In one exemplary embodiment, a first interface isprovided to those individuals involved in the supply aspects of theshipment chain. This interface is referred to as the “source view.” Itcontains a first set of functions for interacting with the shippingservice. A second interface is provided to those individuals involved inthe receiving aspects of the shipment chain. This interface is referredto as the “destination view.” It contains a second set of functions forinteracting with the shipping service. A third interface is provided tothe customer, or more generally, the entity that directs the flow ofgoods from the source site to the destination site. This interface isreferred to as the “customer view.” It contains a fourth set offunctions for interacting with the shipping service. Finally, alogistics interface is provided to those personnel associated with thelogistics node. It contains a fourth set of functions for interactingwith the shipping service.

[0127] The system 100 administers the interfaces using the interfaceadministration logic 316 shown in FIG. 3. This logic 316 controls thefunctionality provided to different users based on their membership inone or more of the above-identified classes. More specifically, thislogic maintains a file which correlates user passwords withfunctionality associated with the passwords. Thus, when a user logs ontothe system, this logic associates the user's password with an indicationof their membership in one of the above-identified classes, and thendelivers the interface appropriate to that membership. Of course, if theuser does not belong to any class, the interface administration logicwill prohibit access to system services.

[0128] By virtue of the above-identified features, a user may accessfunctionality appropriate to the user's membership status anywhere inthe system 100. For instance, a customer having appropriate clearance toaccess the “customer view” may access this interface from any computerlocated at any site. However, different business environments may placedifferent constraints on remote access of shipping information. Forinstance, the logistics node may allow users to access highly sensitiveshipping functions only from prescribed sites.

[0129] The ensuing discussion relates to one exemplary application ofthe invention. In this application, the logistics node coordinates theshipment of parts from a source node (comprising a parts-supplying node)to a destination node (comprising a parts-receiving manufacturing node).However, it should be noted that the interface can be used to coordinatethe transfer of any type of product from any type of source node to anytype of destination node.

[0130] A variety of shipping terms appear in the screens discussedbelow. These terms are defined in the following table.

Interface Data Field Glossary

[0131] Actual Arrival Date. The date on which a shipment actuallyarrived at a destination site.

[0132] Actual Arrival Time. The time in which a shipment actuallyarrived at a destination site.

[0133] Actual Ship Date. The date on which a shipment actually shippedfrom a supplier.

[0134] Actual Ship Quantity. The quantity of a specific purchase orderitem that the supplier actually shipped.

[0135] Actual Weight. The gross weight of a purchase order item on ashipment.

[0136] Arriving Now. A checkbox allowing a receiving location toindicate that a trailer has arrived.

[0137] BOL #. A unique identifier for a document that establishes theterms of a contract between the supplier and the carrier.

[0138] Carrier ID. A unique identifier assigned to a carrier company

[0139] Carrier Name. The name of a carrier company

[0140] Carrier Pro #. A unique carrier reference number generated for ashipment.

[0141] Confirmed Quantity. The quantity of a specific purchase orderitem that a supplier (e.g., at the source node) is expecting to ship.

[0142] Confirmed Ship Date. The ship date that a supplier is expecting apurchase order to be shipped. (Or the ship date on which the supplierhas confirmed that a specific purchase order item will be shipped).

[0143] Description. A short description of the part item.

[0144] Expected Arrival Date. The date on which a specific purchaseorder item will arrive at a destination site.

[0145] Freight Pieces. The number of shipping devices necessary topackage a confirmed quantity of a specific purchase order item.

[0146] Master BOL#. A unique identifier for a document that establishesthe terms of a contract between the supplier and the carrier, where twoor more BOL have been consolidated into a single shipment.

[0147] Part. A reference code that identifies a part item, for example,as defined by the customer.

[0148] Priority. A designation given to a purchase order item (e.g., apart) to indicate urgency of delivery.

[0149] Requested Quantity. The quantity of a purchase order item thatthe customer is expecting to be shipped.

[0150] Requested Ship Date. The ship date that the customer is expectinga purchase order item to be shipped.

[0151] Shipment. A sequential number used to identify each recommendedshipment generated.

[0152] Shipping Device. The device or container used to transport apurchase order item on a shipment. Shipping devices include: a box; acontainer; a pack; a pallet; a rack; and a mixed pallet.

[0153] Ship Quantity. The quantity of a specific purchase order itemthat the supplier actually shipped.

[0154] Ship To. The receiving location for a specific purchase orderitem.

[0155] SLI#. A reference code assigned to a shipment.

[0156] Stackable. A Yes/No field which indicates whether a purchaseorder item is stackable.

[0157] Trailer Detail. A button which allows navigation to a TrailerDetail screen.

[0158] Trailer ID. A unique identifier for a trailer (i.e., Truckload orLTL shipment).

[0159] Trailer ID/SMPD ID. A unique identifier for a trailer ( truckloadshipment) or small package (LTL shipment).

[0160] Transportation Mode. The mode of a shipment. Possible modesinclude: TL (truckload), LTL (less than truckload), and SP (smallpackage).

[0161] 3(b). Source Node Screen Presentation

[0162] Once the logistics node 108 determines the user's nodeaffiliation, it may display a Welcome screen. For instance, FIG. 9Ashows a Welcome screen 900 appropriate for users affiliated with thesource node 106. Users associated with the source node are typicallyproduct suppliers, and, in this particular case, a supplier identifiedas “Vendor A.”

[0163] The Welcome screen 900 includes a menu 906 of functions that maybe accessed by members associated with the source node 106. Thesefunctions include a “home” function 908 (for activating the Welcomescreen 900 ), a “shipment confirmation” function 910, and a “shipping”function 916. The “shipment confirmation function” 910, in turn,includes a “shipments to confirm” function 912 and a “view unconfirmedreleases” function 914. The “shipping” function 916 includes a “pendingshipments” function 918. Each of these menu items may include hypertextlinks associated therewith. Accordingly, activating these functions(e.g., by pointing to and clicking on these functions with a mouse orlike device in a conventional fashion) will call up one or moresubscreens associated with these functions (discussed below).

[0164] The Welcome screen 900 also includes a window 904 containing alist of action items. The items are presented in left and rights fields.The left field of items identifies important (or critical) outstandingtasks, such as overdue confirmation orders and shipping notices, etc.The right field of items identifies other activities that should becompleted within the course of the day. In general, entries in window904 may include hypertext links. The user may activate subscreensassociated with these action items by clicking on the links.

[0165] Finally, the Welcome menu may provide help information, such as atutorial regarding the use of the interface. A user may activate thehelp information by clicking on a hypertext link associated with the“Help” text 902.

[0166] The functions identified in the menu 906 will now be discussed,starting with the “shipments to confirm” function 912. The “shipments toconfirm” function 912 allows a user to confirm purchase orders (alsoknow as “releases”) within a limited period of time of the requestedshipment date, such as two days from the shipment date. This function isactivated by clicking on the “shipments to confirm” hypertext link 912.

[0167]FIG. 9B shows different exemplary screen presentations 901 forperforming the “shipments to confirm function” 912. A first screen 920presents a confirmation work queue 926. This queue 926 comprises a dropdown box that provides a “To Do” list of unconfirmed purchase ordersthat need to be confirmed for each “expected ship date/and ship tocombination.” The first screen 920 also presents a table that providesinformation concerning purchase orders, including a part identifierentry (in field 928), part description entry (in field 930), partpriority entry (in field 932), confirmed quantity entry (in field 934),confirmed shipping date entry (in field 936), requested quantity entry(in field 938), and requested ship date entry (in field 940). In a firststep, the interface instructs the user to update entries in the table asdeemed necessary.

[0168] When the user has finished making updates, the interfaceinstructs the user to click on an update icon 941. This prompts thesystem to generate a second table in screen 922. This table presentsinformation regarding shipment plans that have been generated based uponthe purchase order items confirmed in the first step. More specifically,the freight logic 318 (with reference to FIG. 3 and step 528 of FIG. 5)performs this function by evaluating each release item's priority,confirmed ship quantity, packaging information, and containerinformation to determine the number of shipments required and the modeof transportation for each shipment. More specifically, the second tablesets forth the plan by providing a shipment identification entry (infield 944), transportation mode entry (in field 946), part identifierentry (in field 941), description of the part entry (in field 943),confirmed quantity entry (in field 945), number of freight pieces entry(in field 948), shipping device entry (in field 950), actual weight ofthe product entry (in field 952), and an identification of whether ornot the product is stackable entry (in field 954). In a second step, theinterface instructs the user to update entries in the table as deemednecessary.

[0169] The interface then instructs the user to indicate whether theuser approves of the system-generated shipment plan. For instance, theuser may disagree with the shipment plan because it is believed toindicate too few/many shipments, an incorrect transportation mode, etc.If so, the user may click the “No” button in the third screen 924 toindicate disagreement with the plans. The interface will then place theinterface's cursor in the text box 956, thereby allowing the user toenter a detailed description of the shipment plan changes that arebelieved to be necessary. When finished entering the shipment planchanges, the interface instructs the user to click on the confirm button958 to confirm the shipment plan thus formed. Upon confirmation, theproducts are then shipped.

[0170] Another function identified by the menu is the “view unconfirmedreleases” function 914. This may be activated by clicking on thehypertext link associated with this function. This function is usefulwhen a user wishes to view unconfirmed purchase orders outside of theconfirmation window (e.g., in the above example, outside the two-daywindow).

[0171]FIG. 9C shows an exemplary screen 960 for performing the “viewunconfirmed releases” function 914. This screen prompts the user toenter an identification number corresponding to a particular supplier(i.e., source) and then press the “assume supplier” icon 962 to activatea table giving purchase order items associated with the identifiedsupplier. This table specifically includes a confirmed ship date entry(in field 964), “ship to” location entry (in field 966), part numberentry (in field 968), part description entry (in field 970), priorityentry (in field 972), confirmed quantity entry (in field 974), andrequested ship date entry (in field 976).

[0172] In this embodiment, the interface does not allow the user toconfirm purchase orders listed in the “view unconfirmed release” screen.This screen is nevertheless useful because it allows a supplier to moreeffectively plan for upcoming events. This screen also gives thesupplier an opportunity to timely notify the customer node 104 when thesupplier anticipates that it will not be able to fill a particularorder.

[0173] Another function identified by the menu 906 is the “view pendingshipments” function 918. This function is used to view pending shipmentsthat have already been confirmed. This may be activated by clicking onthe hypertext link associated with this function.

[0174]FIG. 9D shows an exemplary screen 980 for performing the “viewpending shipments” function 918. More specifically, as is in the case ofthe screen 960 shown in FIG. 9C, this screen 980 prompts the user toenter an identification number corresponding to a particular supplier,and then click on the “assume supplier” icon 982 to activate a tableproviding confirmed purchase order information pertaining to theidentified supplier. More specifically, the interface displays theshipments that were confirmed for the identified supplier using the“shipments to confirm” function discussed above.

[0175] The table shown in screen 980 contains a “ship to” entry (infield 983), a priority entry (in field 984), a confirmation ship date(in field 985), a carrier identification number field (in field 986), acarrier name entry (in field 987) and an SLI number used to identify theshipment (in field 988). More specifically, the SLI number defines anidentification code assigned by the logistics node 108 to represent aparticular shipment. The interface displays a message “No CarrierAssigned” if the logistics node has not assigned a carrier. Theinterface will display a message “Re-plan Needed” when the shipmentrequires re-planning by the logistics node 146.

[0176] The supplier may further use screen 980 to send a shippingnotice. More specifically, the supplier typically performs this taskshortly after making a shipment. To perform this task, a user clicks onthe button 989, which bears the SLI number of the shipment. This actionactivates the “send shipping notice screen” 990 shown in FIG. 9E. Thepurpose of this screen is also to identify whether (and how) the actualshipment diverged from the planned shipment.

[0177] Field 991 of the “send shipping notice” screen 990 identifiestop-level information concerning the shipment. Namely this fieldidentifies the SLI # of the shipment, a carrier identification number(“Carrier ID”), a carrier name, a confirmed shipment date, a “ship to”destination, a transportation mode, a master BOL number (defining aunique identifier for a document that establishes the terms of acontract between the supplier and the carrier, where two or more BOLnumbers have been consolidated into a single shipment), a carrier Pronumber (a unique carrier reference number generated for the shipment),an actual shipment date, and a Trailer/SMPK identifier.

[0178] Screen 990 further lists each of the products transported in aparticular shipment. Namely, the illustrated table identifies a partentry (in field 992), a part description entry (in field 993), a partypriority entry (in field 994), a confirmed quantity entry (in field996), and a bill of lading (BOL #) entry (in field 997). The shipmentidentified in FIG. 9E contains only one item. However, other shipmentswill contain plural items, and, accordingly, the table would displaythese plural items.

[0179] If the displayed information is correct, the user may instructthe interface to transmit a shipping notice by activating icon 999. Ifthe user determines that the shipment plan is not correct, the user maymake corrections in field 998 of this screen.

[0180] 3(c). Destination Node Screen presentation

[0181]FIG. 10A shows a Welcome screen 1000 appropriate for usersaffiliated with the destination node 102. Users associated with thedestination node are typically recipients of products, such asmanufacturing plants. In this particular case, the interface indicatesthat the user that has logged onto the work station is associated with a“Receiving Location A.”

[0182] The Welcome screen 1000 includes a menu 1006 of functions thatmay be accessed by members associated with the destination node 102.These functions include a “home” function 1008 (for activating theWelcome screen 900), and a “trailer arrival” function 1010. The “trailerarrival” function 1010, in turn, includes a “trailer arrival” function1012 and a “trailer arrival history” function 1014. Each of these menuitems may include hypertext links associated therewith. Activating theselinks (e.g., by pointing to and clicking on these links with a mouse orlike device in a conventional fashion) will call up one or moresubscreens associated with the identified functions (discussed below).

[0183] The Welcome screen 900 also includes a window 1004 containing alist of action items. The items are presented in left and rights fields.The left field of items identifies important (or critical) outstandingtasks. In the present case, for instance, the window 1004 identifiesthat there are two trailers in the shipping yard having high priorityitems, and that six trailers are waiting to be unloaded for more thanseven days. The right field of items identifies other activities thatshould be completed within the course of the day. In general, entries inwindow 904 may include hypertext links. The user may activate subscreensassociated with these action items by clicking on the links.

[0184] The Welcome menu may provide help information, such as a tutorialregarding the use of the interface. A user may activate this helpinformation by clicking on a hypertext link associated with the “Help”text 1002.

[0185] The functions identified in the menu 1006 will now be discussed,starting with the “trailer arrival” function 1012. Activating thisfunction calls up a screen 1016 shown in FIG. 10B. This screen allowsthe user to view inbound shipments currently in transit. Morespecifically, this screen first prompts the user to enter a codedesignating a destination site, and then click on the icon 1018. Thisprovides a list of transit trailers scheduled to arrive at thedestination site on that current date. The user may examine transittrailers scheduled to arrive on future dates by activating the next dateicon 1020.

[0186] Screen 1016 presents a table that identifies informationregarding the arriving shipments. A first field 1021 in that tableidentifies whether the trailer is “arriving now.” A user may manuallyrecord the arrival of a trailer by locating the appropriate trailerentry in the table, checking the box in the “arriving now” field 1021,and then clicking the update icon 1019. This will automatically populatethe “actual arrival date” field 1027 and “actual arrival time” field1028 in the table with the current date and time. However, a user shouldmanually enter these fields of information in the event that there is asignificant delay from the time that a trailer arrives at thedestination site to the time a user records its arrival via theinterface screen 1016.

[0187] Other fields in the table include an expected arrival date entry(in field 1022), carrier name and identification number entry (field1023), a trailer identification number entry (in field 1024), a masterBOL# entry (in field 1025), a priority entry (in field 1026), and atrailer detail entry (in field 1029). The logistics node 108 may selectthe priority level to reflect the purchase order item in the shipmenthaving the highest priority.

[0188] The priority information is particularly useful to participantsin the shipping chain. In one exemplary embodiment, the table lists thepriority level of the highest priority item within the shipment. Thisfeature quickly reveals loads that may warrant expedited processing toensure their timely delivery.

[0189] By clicking on the detail icon 1029 in the trailer detail field,the interface presents screen 1030 shown in FIG. 10C. This screen 1030allows a receiving location to view detailed information pertaining toan inbound shipment. More specifically, this screen 1030 includes ageneral field 1032 providing high-level information concerning theshipment, including its expected arrival date, the actual arrival dateand time, the name of the carrier, the master bill of lading (BOL) forthe carrier, and a carrier Pro number (a unique carrier reference numbergenerated for a shipment).

[0190] This screen 11030 also provides a table that identifies thedetailed contents of the load. The table specifically includes a partsupplier entry (in field 1034), a part entry (in field 1036), adescription of the part (in field 1038), priority (in field 1040), anactual shipment quantity entry (in field 10420), a bill of lading number(in field 1044), and an SLI number (in field 1046).

[0191] The destination view interface may further permit a user to inputany identifying number (e.g., part number, SLI number, traileridentification number, etc.) and receive information associated withthat number. For instance, a user could input a part number to locatetrailer that current is carrying that part. Alternatively, the user mayenter an SLI number or truckload identification number to examine theindividual items contained in these shipments. Further, after receivinga response to an initial query, the user may “zoom in” on the retrievedinformation to retrieve yet further detailed information regarding theshipment, or “zoom out” on the retrieved information to retrieve moregeneral information regarding the shipment. The logistics node permits auser to retrieve information in this fashion by storing associativelinks between different hierarchies of shipping information (e.g., in arelational database format, or other associative format).

[0192] The above features allow users involved in the distribution chainto track the status of the shipments without having to enter trackingcodes that are unique to individual carriers. That is, users candetermine the status of a shipment by entering various informationpertaining the shipment, but without having to specifically identify thecarrier that is handling the shipment.

[0193] The second function in the destination view interface, i.e., the“trailer arrival history” function 1014, can be accessed by clicking onthat function the menu of functions 1006. This activates the screen 1050shown in FIG. 10 D.

[0194] Screen 1050 resembles the screen 1016 shown in FIG. 10B. Forinstance, it allows the user to specify a destination site by entering adestination code and clicking on icon 1052. It further allows the userto enter an actual arrival date in field 1054 to access trailer arrivalinformation for a specific date. But this interface feature differs fromthe corresponding feature in FIG. 10B by also allowing the user toaccess trailer arrival information for previous dates.

[0195] Screen 1050 displays a table having much of the same informationpresented by in the table of FIG. 10B, including fields 1056, 1058,1060, 1062, 1064, 1066, 1068, 1069 and 1070 identifying the entriesdiscussed in the context of FIG. 10B. Activating the detail icon infield 1069 prompts the interface to generate screen 1080 shown in FIG.10E. Again the information presented in this screen (including fields1082, 1084, 1086, 1088, 1090, 1092, 1094, 1096 and 1098) has beengenerally discussed in the context of FIG. 10C.

[0196] 4(d). Customer Node Screen Presentations

[0197]FIG. 11A shows a Welcome screen 1100 appropriate for usersaffiliated with the customer node 104. Users associated with thecustomer node 104 are typically the parties that command the transfer ofproducts from the source node 106 to the destination node 102 toaccomplish some business objective (such as the manufacture of items forretail sale, such as cars, etc.). In this particular case, the interfaceindicates that the user that has logged onto the work station isassociated with a service parts operation unit, e.g., within amanufacturing company.

[0198] Welcome screen 1100 includes a menu 1106 of functions that may beaccessed by members associated with the customer node 104. Thesefunctions include a “home” function, a “parts information” function1108, a “release management” function 1114, and a “shipment management”function 1120. The “part information” function 1108, in turn, includesan “edit/view party priority” function 1110, and an “add part priority”function 1112. The “release management” function includes an “edit/viewrelease function” 1116. The “shipment management” function 1120 includesan “edit/view shipment” function 1122. Each of these menu items mayinclude hypertext links associated therewith. Accordingly, activatingthese functions (e.g., by pointing to and clicking on these functionswith a mouse or like device in a conventional fashion) will call up oneor more subscreens associated with these functions (discussed below).

[0199] The menu 1106 also includes a number of previously-discussedfunctions 1118. Namely, the “shipment confirmation” and “shipping”functions were discussed above in the context of the source viewinterface. The “trailer arrival” function was discussed above in thecontext of the destination view interface.

[0200] The Welcome screen 1100 also includes a window 1104 containing alist of action items. The layout and function of this window parallelsthe welcome-windows previously discussed (e.g., in connection with thesource and destination view interfaces). Screen 1100 also includes a“Help” link 1102 that functions in the same manner discussed above.

[0201] The functions identified in the menu 1106 will now be discussed,starting with the “edit/view part priority” function 1108. Activatingthis function calls up a screen 1130 that allows the user to view partpriority information and make changes thereto. This function is notshared by the source and destination nodes because, in this particularapplication, the customer node does not wish to empower these nodes tomake such changes. In an alternative embodiment, the system may beconfigured to allow the source and destination nodes to make prioritychanges.

[0202] The screen 1130 allows the user to call up part information byspecifying the part number, supplier information, and/or “ship to”(destination) information. This information is entered into field 1132of the screen, as instructed by prompt 1134. Entry of theabove-identified part information prompts the interface to display yetanother table. This table has lists a part number entry (in field 1137),a part description (in field 1138), a supplier entry (in field 1139),and a “ship to” location (in field 1140).

[0203] The priority field 1141 of the table contains a pull down menu1142. The pull down menu 1142 provides a list of priority levelsappropriate to a particular shipping environment. The lowest entrycorresponds to the least critical priority status. The topmost entrycorresponds to the most critical priority status. The user may changethe priority of any part by activating the pull down menu 1142 andselecting a different priority code than what was originally displayedin field 1141. This changes the urgency attached to the delivery of theassociated part. The change in the priority level is also reflected onthe interfaces accessible to other nodes throughout the distributionchain. Accordingly, changing the priority level here has the effect ofsubstantially instantaneously notifying all parties of changes inpriority.

[0204] Function 1112 performs a similar task to function 1110. Morespecifically, activating function 1112 calls up screen 1150 shown inFIG. 11C. Screen 1150 contains an input field 1154 for specifying a partnumber (or collection of part numbers). The priority of these partnumbers is specified using pull down menu 1156 in a manner similar tothat described above in connection with FIG. 11B. The user formallycommands the system to record the entered priority status by activatingthe “add icon” 1157.

[0205] The other functions (i.e., the “edit/view release item” function1116 and the “edit/view shipment” function 1122) allow the customer toview and edit purchase order information and shipment information,respectively.

[0206] 4(e). Logistics Node Screen Presentations

[0207]FIG. 12A shows a Welcome screen 1200 appropriate for usersaffiliated with the logistics node 108. Users associated with thelogistics node 108 are typically the parties that administer theshipping process. This Welcome screen 1200 includes a menu 1206 offunctions that may be accessed by members associated with the logisticsnode 108. These functions include every function discussed so far, plusa “shipment planning” function 1208, which, in turn, includes a “replanshipment” function 1210. Each of the menu items may include hypertextlinks associated therewith. Accordingly, activating these functions(e.g., by pointing to and clicking on these functions with a mouse orlike device in a conventional fashion) calls up one or more subscreensassociated with these functions (discussed below).

[0208] Activating the shipment planning function 1210 shown in FIG. 12Acauses the display of the shipment planning screen 1230 shown in FIG.12B. This screen is used to make changes to the shipping plan. Shipmentplanning may be appropriate when an initial plan encounters some type ofdifficulty (or the supplier objects to the plan).

[0209] More specifically, this screen identifies a queue of shipments infield 1232 that require replanning. The user may select a particularentry in this list, whereupon that entry is displayed in the table shownat the bottom the screen. The table includes fields 1233, 1234, 1235,1236, 1237, 1238, 1239, 1240 and 1241 that generally correspond to theidentically labeled fields shown in FIG. 9B (i.e., in screen 922 of thatfigure). The user may make changes to the above-identified fields toattempt to resolve the problems with the plan. Alternatively, the usermay activate the “split part” icon 1244 to break up the shipment intoplural part, or the “move parts to new shipment” icon 1245 to transferparts to a new shipment. When finished, the user may activate the“update shipment” icon 1243 to affect formal changes to the shipment'sscheduling plan.

[0210] In an alternative embodiment, the system may automate theabove-described replanning operations. This can be performed by storinga list of rules which capture the decision-making process used by humanoperators (thereby forming a knowledge base of planning rules), and thenaccessing and utilizing these rules to resolve the planning conflicts.

[0211] 4. Variations

[0212] As should be apparent from the above discussion, the presenttechnique generates a great quantity of information concerning shippingevents, and furthermore maintains associative links to reflect therelationships between different fields of information. This informationmay be maintained in database 308 of the logistics node's centralstation. The immediate use of the above-identified data is to providestatus information to participants in the distribution chain (e.g.,suppliers, corporate customers, processing centers, carriers, etc.).Exemplary alternative uses for the above-identified information areidentified below.

[0213] For instance, logic can be incorporated in the system 100 forgenerating interactive reports. The reports can be accessed by customersvia a Web browser to interactively (e.g., using a point an clickapproach) to specify the pieces of information they wish to access andview. Further, the linking of information allows the user to “zoom in”to get progressively more specific detailed information regarding ashipping-related topic, or “zoom out” to get progressively more generalinformation regarding a shipping-related topic. The specific applicationidentified above, for instance, allows a user to “zoom in” to determinedetails regarding the individual items within a load, or to “zoom out”to get more general information regarding the load as a whole.

[0214] Logic can be incorporated in the system 100 to support ad-hocqueries by customers (e.g., free form queries). Additional logic may beincorporated to create customized reports over the Internet that aretailored to the needs of individual customers.

[0215] Logic can be incorporated in the system 100 to supportmultidimensional analysis. This offers the ability to rapidly viewhistorical trends in the shipping data from many different perspectives.For instance, customers can investigate the root cause of shippinginefficiencies by navigating through the linked information provided inthe database to uncover the source of the problem. Further, logic may beincorporated in the logistics node 108 to highlight data that exceeds apredefined threshold or varies significantly from historical trends.This facilitates the user's decision making process.

[0216] Logic can be incorporated in the system 100 to support datamining combs through customer's data, to locate patterns in a series ofpast transactions, and to make one or more recommendations based onthese findings.

[0217] Logic can be incorporated in the system 100 to capture historicaltransportation information for every part/product. On the basis of thisdata, customers will be able to determine the average transit times foreach product from origin to destination by mode. The customers may usethis information to make their supply chains more efficient and reduceinventory.

[0218] Logic can be incorporated in the system 100 for measuringsupplier performance criteria. For instance, customers can determine thepercentage of requested parts/products that a supplier sent in the firstshipment. Further, suppliers can determine how long it takes to deliverparts/products after placing an order.

[0219] Logic can be incorporated in the system 100 that permitscustomers to measure supplier performance criteria. For instance, thesystem may provide performance data pertaining to timeliness, etc.

[0220] Logic can be incorporated in the system 100 for capturingfinancial information for transportation-related costs. For instance,the system 100 may provide historical carrier rates to compare againstbenchmarks.

[0221] Other modifications to the embodiments described above can bemade without departing from the spirit and scope of the invention, as isintended to be encompassed by the following claims and their legalequivalents.

What is claimed is:
 1. A logistics node for administering the shipmentof a product from a source node to a destination node, comprising: aninterface unit for coupling the logistics node with at least one remoteentity; a processing unit coupled to the interface unit for controllingthe operation of the logistics node; a database coupled to theprocessing unit for storing information pertaining to the shipment of aproduct from the source node to the destination node; interfaceadministration logic for permitting a first class of users to interactwith the logistics node using a first interface, the first interfaceproviding access to a first set of functions, and for permitting asecond class of users to interact with the logistics node using a secondinterface, the second interface providing access to a second set offunctions, and wherein the first set of functions differs from thesecond set of functions, and wherein the first set of users areaffiliated with the source node and the second set of users areaffiliated the destination node.
 2. A logistics node according to claim1, wherein the first set of functions includes a function that permitsthe users belonging to the first class of users to view an unconfirmedproduct order.
 3. A logistics node according to claim 1, wherein thesecond set of functions includes a function that permits users in thesecond class of users to view a shipped load which has arrived at thedestination node.
 4. A logistics node according to claim 3, wherein thefunction that permits the users to view the shipped load permits theusers in the second class of users to view a list of products in theload.
 5. A logistics node according to claim 4, wherein at least two ofthe products identified in the list originated from separate sourcenodes.
 6. A logistics node according to claim 1, wherein the interfaceadministration logic further permits a third class of users to interactwith the logistics node using a third interface, the third interfaceproviding access to a third set of functions.
 7. A logistics nodeaccording to claim 1, wherein the third set of functions includes afunction that permits the users to change a priority level associatedwith at least one product, wherein the first, second and thirdinterfaces present priority information that reflects the change in thepriority level.
 8. A method for administering the shipment of a productfrom a source node to a destination node, comprising: providing afreight management tool to users belonging to a first and second classof users; providing users of the first class a first interface withwhich to interact with the freight management tool, the first interfaceproviding access to a first set of functions; providing users of thesecond class a second interface with which to interact with the freightmanagement tool, the second interface providing access to a second setof functions, wherein the first set of functions differs from the secondset of functions, and wherein the first class of users are affiliatedwith the source node and the second class of users are affiliated thedestination node.
 9. A method according to claim 8, wherein the firstset of functions includes a function that permits the users belonging tothe first class of users to view an unconfirmed product order.
 10. Amethod according to claim 8, wherein the second set of functionsincludes a function that permits users in the second class of users toview a shipped load which has arrived at the destination node.
 11. Amethod according to claim 10, wherein the function that permits theusers to view the shipped load permits the users in the second class ofusers to view a list of products in the load.
 12. A method according toclaim 11, wherein at least two of the products identified in the listoriginated from separate source nodes.
 13. A method according to claim8, further including the step of providing users of a third class athird interface with which to interact with the freight management tool,the third interface providing access to a third set of functions offeredby the freight management tool.
 14. A method according to claim 13,wherein the third set of functions includes a function that permits theusers to change a priority level associated with at least one product,wherein the first, second and third interfaces present priorityinformation that reflects the change in the priority level.
 15. Alogistics node for administering the shipment of a product from a sourcenode to a destination node, comprising: an interface unit for couplingthe logistics node with at least one remote entity; a processing unitcoupled to the interface unit for controlling the operation of thelogistics node; a database coupled to the processing unit for storinginformation pertaining to the shipment of a product from the source nodeto the destination node; logic for providing a user with an option toexamine shipment information using first and second levels of detail,wherein the second level of detail is more refined compared to the firstlevel of detail; logic for allowing a user to select the first or secondlevel of detail; and logic for providing shipping information to theuser corresponding to the selected level of detail.
 16. The logisticsnode of claim 15, wherein the first level of detail provides informationconcerning a shipment load, and the second level of detail providesinformation pertaining to an individual product on the shipment load.17. A method for administering the shipment of a product from a sourcenode to a destination node, comprising: providing a freight managementtool to a user; providing the user an interface with which to interactwith the freight management tool; providing the user with an option toexamine shipment information using a first level of detail; providingthe user with an option to examine shipment information using a secondlevel of detail, wherein the second level of detail is more refinedcompared to the first level of detail; allowing a user to select thefirst or second level of detail; and providing shipping information tothe user corresponding to the selected level of detail.
 18. The methodof claim 17, wherein the first level of detail provides informationconcerning a shipment load, and the second level of detail providesinformation pertaining to an individual product on the shipment load.19. A logistics node for administering the shipment of a product from asource node to a destination node, comprising: an interface unit forcoupling the logistics node with at least one remote entity; aprocessing unit coupled to the interface unit for controlling theoperation of the logistics node; a database coupled to the processingunit for storing information pertaining to the shipment of a productfrom the source node to the destination node; and logic for permittingat least one user to change a priority level associated with at leastone product.
 20. A method for administering the shipment of a productfrom a source node to a destination node, comprising: providing afreight management tool to a user; providing the user an interface withwhich to interact with the freight management tool; providing the user,through the interface, with information that identifies a priority levelassociated with at least one product; providing the user, through theinterface, with an opportunity to change the priority level; andmodifying the priority level in response to a user's change in thepriority level to produce a modified priority level.
 21. A logisticsnode for administering the shipment of a product from a source node to adestination node: an interface unit for coupling the logistics node withat least one remote entity; a processing unit coupled to the interfaceunit for controlling the operation of the logistics node; a databasecoupled to the processing unit for storing information pertaining to theshipment of a product from the source node to the destination node; andtracking logic for receiving an inquiry from a user regarding a shipmentbeing made by at least one of a plurality of possible carriercandidates, and in response thereto, providing information pertaining tothe shipment, wherein the inquiry does not require a user to specifycarrier-specific information to successfully retrieve informationregarding the shipment.
 22. The logistics node according to claim 21,wherein the inquiry identifies a product being shipped in the shipment.23. The logistics node according to claim 21, wherein the shipmentinvolves transferring a load from a first carrier to a second carrier ata cross dock node.
 24. A method for administering the shipment of aproduct from a source node to a destination node: providing a freightmanagement tool to a user; providing the user an interface with which tointeract with the freight management tool; and receiving an inquiry froma user regarding a shipment being made by at least one of a plurality ofpossible carrier candidates, and in response thereto, providinginformation pertaining to the shipment, wherein the inquiry does notrequire a user to specify carrier-specific information to successfullyretrieve information regarding the shipment.
 25. The method according toclaim 24, wherein the inquiry identifies a product being shipped in theshipment.
 26. The method according to claim 24, wherein the shipmentinvolves transferring a load from a first carrier to a second carrier ata cross dock node.